SCS Events

Event Logging - SCS v4.x to v5.1.0

Help for those migrating from SCSv4 Events to the modern framework.

The main purpose of the modern SCS Event Logger remains the same as the prior versions.  To that end many of the things you have learned to love (or hate) have been carried over into the new system.  After consultation with users we have attempted to add features which have been missing while trying to keep the user interface as similar and streamlined as possible, fixing issues and making areas more intuitive along the way.

 

Building an Event Template

Meta Items

• Tab Groups have been removed, instead a new UI builder is available to allow you to structure your Event screen as you see fit.
• Manual, Sensor and Summary meta items all have migrated over into the new framework. 
  • "List Of Values" is now called "Selection Options"
  • "Date & Time" has been pulled out into it's own type
  • "Beaufort Scale" has been removed

 

Outputs

• Output to a file/device/socket has been removed

 

Buttons

• Buttons have been re-termed as Manual Triggers
• There are no explicit start or stop buttons
  • The event starts automatically when launched and is stopped via a special Action
• Button groups are no longer limited to 2 buttons.
• Buttons no longer directly manipulate Meta Items or Outputs, instead they start Action Sequences.

 

 

Monitors and Alarms were not actually implemented in v4 however they are in v5.1.0 via the Auto Trigger and "Alarm" action respectively.

 

 

The dependency report is now part of the "Validation" tab.

 

 

Many of the features from OEL have been included in the new system such as:

• The ability to specify colors
• The ability to group multiple manual triggers (buttons)
• The ability to set a forced press order, allow multiple presses, allow for repeating sequences for manual triggers

 

 

Running an Event Template

Event Templates are managed via a website now.  The new framework allows multiple users all over the ship to simultaneously participate in a single event, no more 'local machine only' approach.  You can join, leave and return to an event without having to start it over, even if the server reboots the event should pick up where it left off.  Event data is saved into the database and must be exported / downloaded by a user before it can be worked on.  Note anyone with appropriate rights can download the results of an event, it is no longer required to have mapped drives or for the ship [ET/ST] to put everything together to provide to the PI as they can now do it themselves on demand.

 

 

 

 

SCSv5                                                                                                        Page 1 of 1